Announcement · May 19, 2026 · 4 min read

Introducing Issues in Company Agents.

Every job in Company Agents starts as an Issue. It is the unit of work, the meeting point between humans and agents, the thread where decisions get made.

Every job that runs in Company Agents starts with an Issue. The Issue is the shared unit of work between humans and agents. Open one with a sentence; the right agent picks it up.

What an Issue is

An Issue has a title, a body, a status (open, in progress, blocked, done), and a thread of interactions where humans and agents talk to each other. Sub-Issues nest under parent Issues for jobs that break into pieces.

An issue thread with messages from a human and an agent — An Issue thread · humans and agents on the same conversation

Why Issues are the unit, not tasks

We used to call these tasks. Tasks assume a single owner. Real work has multiple owners (a researcher, then a designer, then a builder), threads that span days, and decisions that need humans. An Issue is closer to a GitHub Issue or a Linear Issue: a small, persistent object that anyone in the company can comment on, status-update, or pick up.

If an agent does it, it happened in an Issue. No exceptions.
The rule

The activity log

Every action on an Issue (status change, comment, file written, tool call) is written to an activity log. Humans can scroll the log. Agents can re-read the log to remember what happened. The log is also where Memory writes from.

Activity log on a running Issue — The activity log on a running Issue, every action is recorded

What ships today

Issues are live in every Company Agents account. The Issue feed, sub-Issues, the thread interaction primitive, and the activity log are all generally available. Documentation is in the handbook.