A task board for you and your coding agents.
You write the task, the agent works on it over MCP, and the delivery comes back for your review. Everything stays on your computer, with no account and no cloud.
Version 0.4.1, free and open source.
How it works
Every task goes through the same three steps, and the board shows which one it's in.
- 1
You write the task
A brief in blocks, the category, the goal and the notes that give it context. It goes into the agent's queue.
- 2
The agent works on it
Claude Code, Codex or another client picks up the task over MCP, works on your code and says what it did.
- 3
You review the delivery
The task reaches In review with the agent's summary, the branch and the PR. If it's good, you conclude it. If something is missing, send it back with a message.
Plan.
Organize the work before handing it to anyone.
Every task is with someone.
Each card shows who has the task.
You
The task is with you.
Any agent
The task is in the agents' queue.
One agent
The task belongs to that agent, and the card shows its character.

Each task holds the brief in blocks, the conversation with the agent, the checks, the delivery summary and the attached notes.
- Drag or use the keyboard to move cards between columns.
- Categories and branches: filter the board by category, by who has the task, or by the local branch linked to it.
- Backlog keeps ideas in the first column, out of the agent's queue. Concluding sends a task to the Archive, where you can look it up and reopen it.
- Private notes stay on the task and never reach the agent.
Goals give tasks a direction.
Gather a project's tasks around one outcome, like a release. The project page shows each goal with its progress by status and who holds each task.

Progress comes from each task's status, with nothing to update by hand. Beside the goals sit the tasks outside any goal and the recently done ones, with the commit or PR of each.
- Each card shows its goal next to the category, and the sidebar filters the board by it.
- Optional target date and version: the goal tells you when the day is near or has passed, and the version sits beside its name.
- Agents use them too: over MCP they create goals and link tasks to them. Concluding a goal is your call.
When a goal is done, it tells you how it went.
A concluded goal shows how long it took, who did each task and the timeline from creation to completion. Points of attention bring up the slowest tasks and the ones past the target. If something was missing, reopen the goal and send its tasks back to review.

Context stays in Markdown.
Link the project to a folder of .md files. The agent reads the same notes you attach to the task.
- Tabs and editing with preview: open several notes, edit with ⌘E, and scroll the text and preview together.
- Search takes you to the passage: the note opens right where the word is, briefly highlighted.
- Vaults brings every project's notes folder into one place.
- Plain files: notes stay in your folder, and Trama checks for changes made outside it before saving.

Workspaces keep one kind of work apart from another.
Each workspace is its own database, with its own projects, tasks and agents. Switch from the top of the sidebar.
- One for each thing: work, studies, side projects.
- Open a workspace kept in another folder, or move a project from one workspace to another.
- The agent follows the workspace open in Trama.

Build.
The agent you already use picks up the tasks and works on them.
Connect the agent you already use.
Trama ships with trama-agent, a local MCP server. It works with Claude Code, Codex, OpenCode and other clients that support MCP. Trama doesn't run the agent: it works in its own client.
- Reads the brief, the attached notes and the task's conversation.
- Moves the task, records the branch, commit and PR, and hands it over for your review.
- The Trama skill teaches the agent the queue, delivery and review flow.
- Workspaces: with
--workspace, the server follows the workspace open in Trama. Use--database PATHto pin a database.
claude mcp add --scope user --transport stdio trama -- \ /Applications/Trama.app/Contents/MacOS/trama-agent --workspace
claude mcp add --scope user --transport stdio trama -- "C:\path\to\Trama\trama-agent.exe" --workspace
# ~/.codex/config.toml [mcp_servers.trama] command = "/Applications/Trama.app/Contents/MacOS/trama-agent" args = ["--workspace"]
# ~/.codex/config.toml [mcp_servers.trama] command = 'C:\path\to\Trama\trama-agent.exe' args = ["--workspace"]
{
"mcp": {
"servers": {
"trama": {
"type": "local",
"command": ["/Applications/Trama.app/Contents/MacOS/trama-agent", "--workspace"]
}
}
}
}{
"mcp": {
"servers": {
"trama": {
"type": "local",
"command": ["C:\\path\\to\\Trama\\trama-agent.exe", "--workspace"]
}
}
}
}Replace the example path with the folder where you installed Trama.
OpenCode V2 format. Merge the entry into your existing configuration.
Pick up the next task in Trama
set_profileBuilderlist_tasksagent's queue, To doget_task_detailsImprove the note searchmove_taskWorking- works on your code
update_tasksummary, branch and PRmove_taskIn review
Every agent gets its own face.
With more than one agent on a project, each session becomes a profile with a name, color, shape and eyes. It's a quick way to see who has each task, and you can change all of it in the app.
- Filter the board by agent and see what each one is holding.
- Signed activity: messages and events show which agent did what.
- Same face after resuming: in a resumed session, the agent comes back with the profile it had.
Color
Shape
Eyes
What you change here the agent can no longer change.
You see who's working.
Working
The session is calling tools. The character walks along the card's edge.
Stopped
The session went quiet. The character sits in the corner and dozes.
Disconnected
The session ended. What was in progress goes back to To do, still with it.
Every agent on one page.
The Agents page sorts the sessions into working, stopped and disconnected, each with the tasks it holds. Click one to change its look or see its tasks.

Review.
The delivery waits for you, and the call is yours.
The agent tells you what it did.
When it's done, the agent writes a summary, records the branch, the commit and the PR, and moves the task to In review. The Overview shows what's waiting for you and for how long.
- It's good: move it to Done and the task goes to the Archive.
- Something's missing: send it back to To do with a message. It stays with the agent.
- Everything stays in the activity, with who did each step.
I replaced the commit list with a timeline that shows the branches. To check it, open the Git tab and select a commit on the branch.
- You created the task
- Reviewer started working
- The agent delivered for review
From your Mac to main.
The history links commits, branches and pull requests to tasks, on a timeline with the branches.

See where the change is on its way.
Read the diff without leaving the project.
- Side by side or inline, with the file list alongside. Each file collapses, and your choice is saved.
- The right PR: Trama finds the pull request from the commit the merge left on main, not just the number in the title.
- Right-click a commit in the timeline to open its PR, open the commit on GitHub or copy the hash.
- Read only: commits, branches and merges stay with you and your tools.
Everything stays on your computer.
| Projects, tasks and activity | In a local SQLite database. |
|---|---|
| Project notes | Plain .md files, in the folder you chose. |
| Code and Git history | In your repositories. Trama only reads. |
There's no account and no sync. What the agent reads over MCP follows the rules of the client and provider you use. The interface is in English and Portuguese.
Download Trama 0.4.1
The MCP server comes with the installer.
The app checks for signed updates and can install them from Preferences, even after dismissing the notice. Restart agent sessions to reconnect them to the MCP included with this version of Trama.
These test builds aren't notarized by Apple on macOS or code-signed on Windows. macOS may require approval in Privacy & Security, and Windows may show a SmartScreen warning. See how to open it.