Track sessions per project

A project is the purpose; sessions are the workers that come and go. Tedix ties each local Claude Code or Codex session to a Work project so the owner sees progress by project instead of by terminal window.

What a session reports

These features work for every signed-in organization member with the Tedix plugin and CLI hooks. No particular user, administrator role, coordinator name or pre-seeded board is required. Install the plugin through your host, select your organization, then opt in on this machine:

tedix setup agents context enable-decision-capture --project <project-id>

The project is your inbox for sessions outside a bound repository. Repository bindings take precedence. This opt-in enables the private request ledger and session status reporting in that organization; the first uploaded event or status creates your own records. TEDIX_AGENT_STATUS=0 or an explicit "enabled": false in ~/.tedix/agent-status.json disables status reporting. Use tedix setup agents context disable-decision-capture to stop new session ingestion; that does not delete records already uploaded. Status separately enabled in agent-status.json remains independently enabled.

With the Tedix CLI (0.8.8 or later) and its status hook enabled, every session reports a short status record to your organization at turn and lifecycle events. Since CLI 0.8.8 the record carries:

A change of name or binding is reported as its own event. The server keeps a project or Work Item only when it belongs to the caller’s organization. The hook sends no transcript content; the summary is the last line it recorded.

Enable the hook with TEDIX_AGENT_STATUS=1 or "enabled": true in ~/.tedix/agent-status.json. Bind the checkout with tedix setup agents context bind and select an item with tedix setup agents context select <id>; the CLI reference covers both. Binding is correlation, not execution authority: a bound session still needs an admitted Attempt before it may change a Work Item.

Where Tedix OS shows it

Independent local sessions register with tedix lane start "<title>" --project <project-id> after bootstrapping their own agent identity. Registration uses ordinary Work admission and a bounded heartbeat; lane done or lane fail settles that same session’s Attempt. A host’s subagents share its Attempt. Transcript-reported lanes without registration appear as unconfirmed activity, not as admitted or running workers.

For an optional scheduled document, install the repository’s apps/skill-runtime/examples/living-status-board example in a private workspace owned by the member and grant that skill read access to Session activity. Its parameters hold the destination, owner, time zone and schedule. The first run creates that member’s Session activity document; later runs reuse it. It is a snapshot, not the live Attention feed. Installing the plugin does not create or activate a scheduled skill.

Session ingestion and privacy

With decision capture enabled, capture-reply uploads the message you type and capture-stop uploads the assistant’s turn text, delegated reports and a bounded digest of tool failures and lane activity. Events also carry the host session id, repository name and timestamp. Prompt text is bounded to 8,000 characters and activity to 4,000; assistant turns include the full redacted turn text. This is content upload, not anonymous telemetry.

Before upload or storage in the local retry outbox, the CLI removes known credential patterns and applies the decision-capture redaction rules. Redaction is best effort: ordinary prose can contain private information. A failed upload stays in a private local outbox for a later hook to retry. No capture occurs for unattended runs. Disabling capture prevents new uploads, including pending outbox retries, until capture is enabled again.

Uploaded message text, derived request text, session summaries and proposed recovery lessons are private to you in the selected organization. Other members, including organization admins, can see project lane titles, attention states and explicit shared Work records, but cannot read your private message text or summaries through Contributors, Attention or the request-ledger APIs. A failed turn classification never copies the turn into a shared Work comment.

Sharing is a separate action. You may share information explicitly in Work or grant a particular scheduled skill access to your Session activity resource. That grant is checked against the actual run and can be revoked; a private workspace keeps the derived document private too. Merely being an org admin does not supply that grant. Opt-in capture also creates questions addressed to you in Interactions; unrelated members cannot read their bodies.

Automatic request filing

Enable automatic filing from a personal Sessions app for your ledger in the selected organization. Capture alone does not enable sharing. Enabling filing allows concise container briefs and proposed Work to be visible to the organization, along with corrected filing examples that teach project routing. Uploaded source events remain private to you. Turn it off from the same page to stop further automatic filing.

Each new request, ask, idea or issue is compared with project and objective briefs, factory bindings, visible workspaces and recent Work. A small Workers AI model picks a candidate and Clef-flash scores whether it fits. A score of at least 0.8 files to the existing project. A lower score creates a plainly named project with a one-line brief, or a private workspace linked to that project. A recurring-work suggestion becomes a factory proposal; it does not start a schedule. Actionable rows create proposed Work or reuse a matching item. Filing grants no execution authority and never answers a pending human ask.

Attention shows filed to X by auto, the fit score and the reason. Unfiled becomes a review queue for low-confidence filings. Move or undo a filing there; the correction is saved as an example for that project’s future routing and a lesson proposal in the existing learning pipeline. The page also shows the past week’s auto-filings and the fraction subsequently corrected.

Generated containers carry an auto-created marker. Attention lists projects and private workspaces that are empty after 14 days for cleanup; it does not silently delete them. Classification runs through the existing queue, in bounded batches with retries. Pending rows remain visible during an outage.

A project’s bucket on the Portfolio comes from the project’s metadata field portfolioBucket; archived and done projects, and projects with no recognised bucket, fall under “Other”. Placeholder briefs read as empty.

A typical day

1. The owner opens Work. Feed shows ranked updates with receipts; Office’s Your requests section holds their unfinished chat requests.
2. A session that cannot continue reports “waiting for you” and the question appears in the Deck.
3. The owner answers in Tedix OS; the session’s host picks up the answer and the project page moves the contributor back to “working”.
4. A new session in the same checkout inherits the binding and shows up as a second contributor on the same project.

Limits

• Only sessions on machines with the CLI hooks installed report. Claude chat and the ChatGPT desktop app have no local hooks, so they do not appear as contributors unless they hold an Attempt.
• Contributors list sessions, not people. A session key is <harness>:<host session id>.
• Idle, and ended after 12 silent hours, are derived from age when read; nothing is swept. On a project page, a contributor with no report or Attempt heartbeat for 24 hours reads as ended, whatever it last reported.

Related: Factories, Workspaces and Projects, Core concepts.

Arrange a session activity app

Attention combines local Claude and Codex sessions, cloud tedi turns, factory and skill runs, and scheduled skill coordinators. Its two-hour timeline ends at each lane’s latest confirmed heartbeat. Elapsed timers keep ticking while work is open; finished work keeps its final duration. A fading dot and a “no heartbeat” label distinguish silent work from fresh reports. A silent local session may mean a closed laptop; silence alone does not prove that. Cloud work runs independently of your laptop.

Today’s contribution bar shows the share of reported time in the bounded overview, with overlapping work counted separately. Select a source, tedi or factory to narrow the view. Waiting work appears before blocked, moving and backlog work. Unfiled remains the review queue for captured requests without a project match.

Use Focus today to describe what matters. It helps rank cards and provides a relevance hint to the automatic project classifier; uncertain matches still stay unfiled. Arrange view pins projects, focuses one project, hides columns, changes spacing and moves widgets. The composition is a versioned per-user, per-organization config row, shared across devices. Concurrent edits return a conflict instead of overwriting each other.

A chat assistant acting through your authenticated connection can read get_attention_layout, then call update_attention_layout with the complete layout and its expectedRevision. No owner id is accepted. Your own active personal tedi can edit the same row: Tedix checks its owner binding and the owner’s active membership on each call. A tedi cannot select another owner. The same controls are available as browser tools while the app is open.

A workspace app with manifest entry tedix:app/attention embeds the same renderer. It shows the workspace’s linked projects, its factory executions and its conversation activity, after checking workspace access. The unfiled queue is available when the app is configured with scope: "personal". Returning shows updates since your previous visit, using a server-side visit marker shared with your phone. Visit tracking is best effort when the connection is unavailable.