Activity

Activity shows who's working right now and what happened in the project: where the work stopped, every session with your AI agent and the reports you use to hand the project off. It's all built from your agent's sessions, without AI. The only part the agent writes is the handoff note.

There are four tabs:

The conversation belongs to whoever ran the session

What you ask the agent, what it replies and the commands it runs stay with you only. Nobody on the team can read them, through the dashboard or directly in the database.

The team sees a summary of your sessions: when it happened, how long it lasted, the branch, how many requests there were, the files that changed, the commits, the completed tasks and the handoff note. That's enough to know where the project stands without reading anyone's conversation.

The same goes for the agent. At the start of a session, your agent receives the summary of the project's last session. If someone else ran that session, the agent gets the files, commits and handoff note, but not their requests.

Keys and passwords the agent read or typed (when opening .env, for example) are replaced with *** before anything leaves your computer.

Now

Who's working on the project at this moment. Each teammate gets a card when they have the project open in the dashboard or have an agent running. Inside the card you'll see each of their agents, with:

• What it's doing: thinking, editing a file (with its name), running a command (with a short description, never the full command), Needs you (it asked for permission or asked a question) or waiting for the next request.
• Which skill it's using, when the agent is inside a Faundr command (for example, /faundr:design shows as Design). This lasts from the moment you type the command, or the agent calls the skill, until it finishes its response.
• Where it's running: the agent (Claude Code or Codex), the computer name and the branch.

Everything updates live. An agent that hasn't reported in for 15 minutes shows as "No updates" (the terminal may have been closed without notice). After 2 hours, it disappears from the tab. To change the computer name that's shown, add "machine": "Ana's laptop" to ~/.faundr/config.json.

Requests and notes

Below the people who are working you'll find the requests. There are two kinds:

• Request: a task for an agent to do. Describe what needs doing, choose who it's for (a teammate, yourself or anyone) and send it.
• Note to agents: information only, with nothing to do. Example: "don't touch the payment module today". It reaches the next open agent of anyone on the team, along with their next request, and shows as done once it's delivered.

About requests:

• A request reaches the person's open agent with their next request, or when the agent finishes what it's doing. If nobody has an agent open, it arrives when the person opens one.
• A request from someone else only runs with the OK of the person at the computer. The agent shows who asked and what, and asks. A request you send to your own agent runs right away.
• Each request shows its state: waiting, delivered to the agent (and on which computer) or done, with a line about what was done. You can cancel a request that hasn't been delivered yet.
• Messages between sessions also show up here. One person's agent can send a message to someone else (faundr msg).
• To fetch requests right away, ask the agent for /faundr:inbox. To have it check on its own every few minutes: /loop 5m /faundr:inbox.
• The Open, Done and All filters and the search box help you find a request or a person.

Working as a team

When more than one person works on the project at the same time, Faundr makes sure nobody breaks anyone else's work. It warns and never locks:

• Alone in the project: nothing changes.
• Someone is already working when you arrive: at the start of the session, the agent tells you who's in the project and asks whether it can open a separate workbench for you, explaining what could get in the way. Nothing happens without your yes, and any work you haven't saved yet comes with you to the workbench.
• Whoever was already working finds out with their next request: "Ana joined the project and is working on X".
• Before editing a file someone else touched in the last hour, the agent is told who it was and what they're doing.
• Merging the work: when the task is finished, the agent asks whether it can merge into the main project. With your yes, it pulls the latest version, merges, runs the tests, resolves conflicts and explains them in plain language (or asks when it isn't sure), then pushes (/faundr:merge). While someone else is active, pushing straight to the main project needs your confirmation.
• Task owners: faundr claim "<task>" puts your name on the task in the dashboard. If someone else tries to take it, their agent gets a warning and asks first. faundr release frees it up again.
• Feature owners: whoever creates or starts a feature becomes its owner. If someone else's agent is about to work on it, the agent says who owns it and only continues with a yes (see Features).
• Two of your agents in the same folder: the second one asks whether it can create a separate copy of the folder so one doesn't undo the other's work.

To merge two people's work, the project has to be on GitHub. If it isn't, the agent offers to help set it up. To see who's in the project from the terminal: faundr team.

Where you left off

This tab shows:

• Last session: date, duration, branch, the handoff note and the session summary: what was requested, how many files changed, the commits, the completed tasks, what was recorded and how it ended.
• Still to do: open tasks by feature and open concerns.

If someone on the team has the agent open right now, a "session in progress" label appears.

It's the same information the agent receives at the start of the next session, and the same one /faundr:resume summarizes.

Session log

One row per conversation with your agent, newest first, 10 per page. Each session shows:

• date, start, end (or "now", if it's still open) and duration;
• branch and agent (Claude Code or Codex);
• the handoff note;
• the summary: requests, files, commits, tasks;
• Raw events: everything the plugin recorded, for anyone who wants the detail.

In other people's sessions, requests show only as a count ("Asked (5)"), and the raw events leave out the conversation and the commands. You only see the files and commits.

Sessions with no requests at all (opened and closed without being used) are hidden. Use the link to show them.

Reports

Weekly summary

The last 7 days in plain language, for people who don't code: what moved forward, what got finished, the problems and the cost. Use it to update partners and investors.

• Copy summary and Regenerate.
• Automatic delivery: every Monday morning, the summary goes to Slack or Discord. It uses the same addresses (webhooks) set up in Errors → Live app. Turn it on or off with Turn on weekly delivery.

Developer handoff

A single document, put together by Faundr, with what a developer needs to take over the project: what it is, where it stopped, where it runs, how to run it, rules, decisions, open risks and the code map.

Use it when you hire someone, ask for help in a community or switch agents. The buttons:

• Download (.md): saves the document to a file.
• Copy document: to paste into an email, a chat or another AI.
• Regenerate: rebuilds it with the project's current state.

From the terminal: !faundr handover --out PASSAGEM.md.

The handoff note

The handoff note is one to three sentences: what's half done, what the next milestone is and anything the next person should watch out for. Example:

Faundr asks the agent for the note at the end of long sessions (4 or more files edited, or about 20 minutes of edits), and again every 30 minutes. To write one whenever you want, use /faundr:handoff, with or without what you want to record.

The note appears in Where you left off, on the project card on the home page and at the start of the agent's next session.

Commands