Portfolio
Every client and project, in one place.
Organizations and their projects sit side by side with open tasks, billing, and tags. Each one has a page with a README, files, a year of tracked activity, and an LLM.txt that briefs your agents.
Organization
TagHighlights
Clients, agencies, and you
An organization is any company you work with or for, including your own. Cross-client tags such as agency or internal group them, their projects, and tasks.
Keys that follow the prefix
Each prefix counts its own tasks, like NWR‑142. A project can share its organization's prefix or have its own, and a moved task's old key keeps working.
A briefing for your agents
LLM.txt holds the conventions and background agents need. Kernel adds it to Codex and T3 Code handoffs and serves it through the Agent API.
Moving projects
Move a project and its work, after a review.
Moving a project to another organization starts with a review of what changes: tasks, task keys, time entries, and the settings it inherits. Nothing moves until you confirm.
- Tasks take the new prefix's next numbers; their old keys keep working
- Finalized time entries stay where they were recorded
- Inherited color, calendar, hours, and billing terms are spelled out
LLM.txt
Brief your agents once, per client or project.
LLM.txt is Markdown you write for AI agents: conventions, background, and where to look. Kernel adds it to agent task handoffs and the Agent API, and shows it nowhere else in the app.
- Up to 50,000 characters for each organization or project
- Handoffs link to the current version instead of copying it
- Files and added tabs are listed for agents alongside it
LLM.txt for Northwind Robotics# Northwind RoboticsLogistics robotics client. Dana Ito approves scope; Ari Sato owns the fulfillment API.## Conventions- Branches: nwr/<task-key>-short-name, one task key per pull request.- Every release gets a second review before launch.## Where to look- The webhook retry spec and the SOW are in Files.- Staging runs at staging.northwind.example. Never test against production.Markdown. Describe conventions, background, and where agents should look.388 / 50,000DiscardSaving…Good to know
- Projects are Active, Completed, or Archived; one completes only when no unfinished tasks remain.
- Completing a project keeps its tasks and recorded time and stops new automatic scheduling.
- Task prefixes are 2 to 8 letters or numbers, unique in the workspace; TASK and MEETING are reserved.
- Recently opened order is kept in this browser and holds still while you work, so cards don't jump.
- A project takes its organization's color unless you choose a preset or an exact hex color.
- Files can be any type, up to 50 MB each, with every earlier version kept.
