Bring your agents. Keep your direction.
Plan with your team. Build with Codex and Claude. Keep issues, coding sessions and reviewed changes connected in one workspace.
The plan. The code.
The next step.
Explore the current Servlet workspace, from shared priorities to the coding brief that moves them forward.
From a clear brief to a reviewed change.
Choose Codex or Claude, keep the brief and stage documents together, and move through research, design, planning, implementation and review at your pace.
Illustrative example data. No live agent run.
DESKTOP · WEB · YOUR RUNNEROne plan.
One plan.
More ways to work.
Keep the team aligned wherever you are, and choose where your coding agents run.
A home for your coding agents.
Run Codex and Claude with your existing CLI accounts. Keep conversations, Markdown documents, Git changes and a terminal beside each task.
Get the desktop app ↗macOS and Linux available. Windows signing pending.Keep shared work within reach.
Manage issues, projects, comments and documents in your browser. Add Servlet to your iPhone Home Screen and opt into notifications.
Open the web app ↗Local coding sessions and terminals stay on your computer.Choose where the work runs.
Connect your own runner for isolated remote tasks, queued messages and bounded schedules. Inspect its history and changes from Servlet.
Read the setup boundaries ↓Requires your own host, repositories and provider sign-ins.A WORKFLOW YOU CAN TRYTurn a brief into
Turn a brief into
a reviewed change.
Explore the research-first path below. Servlet also supports a PRD-first workflow and direct sessions.
Interactive illustration.
No agent runs on this page.
THE BRIEF
Add keyboard navigation to the issue board without changing existing mouse behavior.
STAGE 1 OF 5 · Read only
Understand the problem first.
Inspect the project and gather evidence before deciding what to change.
Research documentEXAMPLE
Add a feature
01
Inspect the current implementation
02
Record the problem and supporting evidence
03
List assumptions and open questions
Work together.
Build on your computer.
Keep shared issues, projects and documents in sync across desktop and web. Local coding stays with your files; remote tasks stay on the runner you configure.
Local coding workspace
Project folders and file paths
Coding tasks and session transcripts
Git worktrees, status and diffs
Coding-agent credentials with their CLIs
Your configured CLI may send context to its model provider. Local storage is separate from local inference.
Know what
the agent can do.
Choose the scope, inspect the request and keep delivery decisions in your hands.
TRY AN APPROVAL
One request. Your decision.
- Agent
- Codex
- Command
npm test- Scope
- Example project folder
Waiting for your decision.
Illustration only. No command is executed.A workspace with
room to think.
Connect the everyday work: a shared issue, a focused coding session, and a change your team can review.
Local terminal
Use an integrated terminal in your project folder, alongside the conversation, stage documents and changes.
Documents that follow the work
Edit Markdown and keep research, requirements, design, planning and review documents alongside your task.
Isolated Git worktrees
Give a task its own working directory, then inspect status and diffs. Archived worktrees remain available.
Sessions and saved drafts
Search sessions, save a brief for later, queue follow-up messages, and interrupt or continue work when you need to.
Teams and organizations
Invite teammates, manage access, and organize shared or private teams. Keep personal work and organization work in separate workspaces.
A focused desktop
Find work with the command palette, use keyboard shortcuts and dictation, and choose Graphite or Paper themes.
From issue to coding task
Turn a shared issue into a coding brief, bind its project to a local folder, and see execution claims before starting work.
Plans that stay connected
Track cycles and milestones, post project updates, and see current work in timelines and planning analytics.
Review before sharing
Preview text before publishing it to a shared issue or document. Review GitHub or Jira issue imports before adding them to your team.
Bring the agents you already use.
Choose Codex or Claude, an available model and reasoning effort. Stream the conversation, interrupt when needed, then continue.
CodexClaude
BEFORE YOU STARTA few useful
A few useful
answers.
Understand the workspace,
the boundaries and the next step.
Who is Servlet for?
Developers and engineering teams who already use coding agents and want one place for planning, sessions, context and reviewed delivery.
Which computers does it support?
Desktop downloads are available for Apple silicon Macs running macOS 13 or later, and Linux x64. Windows signing is pending. The download page lists current packages and requirements.
Do I need Codex or Claude installed?
Yes, for coding sessions. Servlet discovers your installed Codex and Claude CLIs and uses their existing configuration and account. Installation detection alone does not prove authentication or model access.
How does agent usage work?
Your selected CLI's configured provider and account determine model access, limits and usage costs. Servlet does not make every model available or include a separate model subscription.
What stays on my computer?
Local project files, coding tasks and transcripts stay in the desktop workspace. Accounts and shared planning records are hosted. If you configure a self-hosted runner, its tasks and history live on that runner. You choose what text to publish to your team.
Is all agent processing local?
The coding workspace is local, but the selected CLI may send context to its configured model provider. Local storage does not imply local inference. Review your CLI configuration and provider terms.
Can a task run or advance by itself?
Creating a task saves its brief. You start sessions and advance stages explicitly. You can also configure bounded schedules: local schedules need Servlet open, and remote schedules need a running self-hosted runner. Shared work is marked Done by people.
How do approvals differ between agents?
Codex supports shell tools and exact pending command or file approvals. Claude supports confined file tools and displays denied permissions. Unsupported permission requests fail closed.
Can I download it today?
Yes. Get the notarized macOS installer or a Linux package from the download page. Windows downloads remain pending signing. You can also sign in to the web app for shared planning.
Can I use Servlet on my iPhone?
Yes. Open app.servlet.ai for shared issues, projects, comments, documents and views. Add it to your Home Screen to use the installed web app and opt into supported push notifications. Local coding sessions, files and terminals stay on your computer.
Does Servlet include cloud hosting for agents?
Remote work connects to a self-hosted runner that you configure with its own repositories and provider sign-ins. An independent host is needed to keep working while your computer is off. Managed cloud hosting is not included.
What happens to conflicting shared edits?
Shared records use version checks and actor-attributed activity. Conflicts are surfaced so you can review the latest version and preserve your draft rather than silently overwrite someone else's work.
Bring your next project into Servlet.
Download ServletAlready installed? Open Servlet ↗macOS · Linux · Web & iPhone