Skip to content
pendlooq

Glossary

One short definition per concept. Each has its own anchor, so you can link to it directly.

Updated

pendlooq

pendlooq is an open-source AI teammate that turns one chat into tasks, works with any model and keeps your keys on your machine. The name is pending + loop; the q stands for queue.

General chat

The single conversation where you talk to the assistant. Messages that become tasks fold into one line with a task chip; the rest stay as ordinary chat.

Stream

A line of work, such as billing, hiring or personal. A stream has its own folders, skills, connectors, credentials, model, notes, permissions and parallel-task limit, and the assistant working on a task sees only what its stream was given.

No stream is a built-in section for one-off tasks: the assistant answers and reasons there, without files or connectors.

Task (thread)

A message, or several messages in a row, turned into a unit of work with a status, a stream and a priority. Task and thread are the same thing: the thread holds the task’s own messages, and only those go into the model’s context.

Router

A cheap service model that reads every message in the general chat and decides: continue an existing task, create a new task, propose a new stream, or leave it as a remark. It searches tasks in all streams and statuses, archived ones included, active in the last 14 days by default.

Its decision shows as a chip under the message, with Undo, Change stream and, for continued tasks, New task instead.

Statuses

Every task has one status that says whose turn it is. Waiting-for-you statuses (Needs me and Review) are counted in amber in the sidebar.

New
The task exists but is not clear enough to start. The assistant asks questions in the thread; it starts on its own once it has enough. New tasks without activity are archived after 7 days by default.
In Progress
The assistant is working. If the stream is busy, the task waits in a queue by priority and shows its place, for example “In Progress (2)”.
Paused
Stopped by you, or by an error such as a rate limit. After an error pendlooq retries with growing delays; after a manual stop, only you resume it.
Needs me
The assistant needs your answer or permission. Reply in the thread and the task goes back to In Progress.
Needs others
Coming with the cloud: the task waits for a colleague’s reply, for example in Slack, and continues by itself when it arrives.
Review
The result is ready. Accept it, or reply to send it back for changes. Accepted automatically after 3 days by default.
Done
You accepted the result. Done tasks are archived after 3 days by default.
Archived
Removed from the board by hand or by the timers above. Archived tasks stay searchable, and a message about the same topic brings them back.
Runner

The module that runs the agent: it takes a task, works on it with the stream’s folders, tools and model, and sends messages and status back. It runs on your machine, holds your model keys and credentials, and connects to the API over a network protocol.

Coming with the cloud: a runner on your own server (Docker image or binary) that connects out to the pendlooq cloud, so tasks run while your laptop is off.

Skill

A folder with a SKILL.md file: instructions the assistant loads when a task needs them. Skills are turned on per stream and installed from a GitHub or GitLab link or a local folder; five come built in.

Connector

A connection to an outside service that the assistant can use as tools, granted per stream with an access level: read only, write with confirmation, or write without asking. Jira, Notion and Google Drive in the client; Slack comes with the cloud.

Credential

A named secret, such as a token or password, stored as an environment variable value in your OS keychain and granted to specific streams. The model sees the name, never the value, and values are removed from command output.

Stream notes and settings

Every stream has a notes file (long-term memory the assistant reads in every task and can extend) and a settings file (agent permissions in Claude’s allow / ask / deny format). If a stream folder already has a Claude Code, Codex or OpenClaw setup, pendlooq reads and extends that instead.

Approval card

The card that appears in a thread when the agent wants to run a command or write to an outside service and the stream’s rules say to ask. It shows the exact action with Allow, Always in this stream, Always in all streams and Deny; while it waits, the task is in Needs me.

Feed

One line for every action the assistant takes: tasks created, status changes, approvals, writes to services, results and errors, filterable by stream and type.

Autolearning: when the assistant adds something to a stream’s notes, the feed shows a “learned” line with a one-sentence summary of what it learned.

Service model

A cheaper model, separate from the main one, that routes messages, writes feed lines and matches skills to new streams. You choose it in Settings → Models.