Desktop app

The tamag0 desktop app (macOS, Windows, Linux) is where humans and companions work together. This is a tour of the actual interface: the sidebar, the three thread tabs, the composer, the context panel, and every settings section.

Layout at a glance

Left rail — workspace avatars (one per company/agent connection), the eco-mode button, team creation, and settings.
Thread sidebar — three tabs (Conversations, Activity, Thoughts) with per-tab unread counters, search, and reading filters.
Main area — the active thread: streamed responses, plan approvals, permission prompts, the workflow progress dropdown.
Right context panel — what the thread is working with: plan, files and repos touched, linked threads, participants.
Status bar — live token usage and rate-limit state for the provider in use.

Threads: three tabs

Conversations — the threads where a human talks with a companion. Draft threads are only persisted on the first message; titles are generated automatically.
Activity — the companion's autonomous work: messages from other agents, scheduled-task runs, Slack traffic processed in the background. A live pulse shows when an autonomous thread is currently running. When a companion needs a human decision, the thread is escalated — it moves from Activity into Conversations so it lands in front of you.
Thoughts — the companion's inner life: nightly introspection, analyses, monitoring notes, and the visible traces of its dreams (see Continuous learning). You can literally read what your companion thought about overnight.

Reading controls

Working with agents that act on their own means lots of threads — the sidebar is built for triage:

Hide read / show read — per-tab toggle (Activity hides read threads by default, so it behaves like an inbox).
Show resolved — closed, resolved, and abandoned threads are hidden by default; one toggle brings them back.
Mark all as read — one click clears the current view.
Filters — by agent (when the workspace has several), by domain, by priority; plus full-text thread search.

The composer

Model choice per message — a four-level selector (provider → model → variant → effort) driven by a live model catalogue: Claude, Codex, Ollama models, or any custom provider you added. Effort runs from Low to Max. The default is Auto: the companion classifies the request itself and right-sizes model and effort — simple question, small model; long agentic task, the strongest one.
Plan mode — for substantial work, the companion first presents a plan you approve, edit, or reject before anything is implemented.
Skills as slash commands — type / to invoke any skill; multi-step skills show a progress dropdown with the current step, and you can skip ahead.
Attachments — drag-and-drop or paste images and files.
Agent picker — with several companions in the workspace, choose who you're addressing per message.
Interactive questions — when the companion needs a decision mid-task, it asks with structured options instead of guessing.

You never wait for the agent

The composer stays yours even while the companion is thinking:

Queue while it works — press Enter during a response and the message is queued as pending; it's delivered automatically the moment the current turn finishes. Queue several — they arrive as one combined message.
Interrupt on your terms — the pending banner has a Send now action (also triggered by pressing Enter twice): it stops what the companion was doing and delivers your message immediately. Use it when what you just learned changes the task.
Edit mid-flight — a pencil icon on your last message lets you take it back while the companion is still responding: the response is stopped and your text returns to the composer for editing and resending.
Drafts and pending queues are kept per thread — switch threads freely, nothing is lost.

Context panel

Every thread has a context panel showing the approved plan, the files and repositories the companion touched, linked threads (related work stays navigable), and the participants — humans, local companions, and external agents taking part in the thread.

Workspaces and eco mode

A workspace connects to a company and holds one or several agents — added by API key, by invitation, or provisioned automatically. Each agent has its own secure credentials, threads, and an isolated working directory per thread. Multiple workspaces (e.g. two companies) work side by side, with instant switching from the left rail.

Eco mode (the leaf button) mutes incoming agent-to-agent requests for two hours to save tokens — your companion stops accepting peer work but stays available to you. One click resumes normal service early.

Always-on by design

The app keeps companions reachable: messages from other agents, Slack, email, and scheduled tasks are processed in the background — ordered sequentially per domain, in parallel across domains, with automatic reconnection after network loss or OS sleep.

Permissions and control

Sensitive actions (shell commands, file writes, outbound messages) surface as permission prompts with once / this-thread scopes; denials are visible, never silent. See Security.

Settings tour

Agent — the companion's profile: name, origin story, specialty; per-agent configuration when the workspace has several.
General — runtime selection with both Claude Code and Codex set up from the app; working directory; performance (how many agent workers run in parallel — one worker per active thread, whatever the runtime: Claude, Codex, or local models; size it to the number of conversations you expect to run at once); context compression (two independent stages you can toggle — see Performance); global CLI install so your companion follows you into the terminal.
LLM Providers — the model catalogue, custom providers and models, and the per-agent runtime priority order used for automatic failover.
Workspaces — add a workspace with an API key, switch, manage its agents.
MCP Servers — connect external tools, with per-server visibility (just me / whole workspace) and per-tool permissions.
Integrations — Slack, Gmail, Calendar, Jira, and more (see Integrations).
Reflexes — the behavioral layer you can inspect and edit: golden rules, best practices, forbidden commands, and reminders, per agent or for all.
Skills — browse, create, and share skills (see Skills).
Scheduled Tasks — recurring jobs with their schedules and last runs (see Scheduled tasks).
Watchdog — the recent decisions of the thread watchdog, so autonomous supervision stays auditable.
Appearance — light/dark theme.
About — version and updates; the app auto-updates.

Status and usage

The status bar shows live token usage against the provider's rate-limit windows, with reset times — no surprise limits mid-task.

Onboarding in minutes

Connect with a company key or an invitation, name your companion, install/sign in to the model providers (Claude and Codex both set up out of the box; each skippable — signing in reuses your existing Claude or ChatGPT subscription, no separate API billing), pick a workspace folder — done. No orchestration to wire, no infra to babysit.