Ticket Terminal
Open Jira and Notion tickets as real local Claude or Codex sessions.
FreeOpen SourceAI AgentsAI Coding17 impressionslaunches Oct 201 comment
Comments
>log in to commentI built Ticket Terminal because the ticket and terminal history kept becoming two separate stories. It keeps Jira or Notion as the source of truth, then opens the ticket as a real local Claude Code or Codex session with the transcript and agent trail attached. This is a public preview. It is single-user, setup still needs an authenticated CLI and tracker credentials, and it is not a sandbox. I’m mainly looking for people willing to try one real ticket and tell me where the setup or workflow breaks.
Ticket Terminal opens Jira or Notion tickets as local Claude or Codex AI sessions with full transcript and cost tracking.
- for
- Developers who want to work on tickets using local LLM agents.
- pricing
- open source
- license
- Apache-2.0
- v0.1.0Ticket Terminal v0.1.0 — Public Preview3 days ago
Key features
- Ticket-to-session conversion — Opens existing Jira or Notion tickets as real Claude Code or Codex sessions.
- Transcript & agent trail — Keeps a full transcript and activity trail attached to each ticket.
- Shared Markdown memory — Provides a persistent Markdown workspace shared across the session.
- Token cost estimate — Shows token-based cost estimates for the work performed.
- Docker distribution — Offers a Docker image for easy, containerized local deployment.
- Host bridge option — Spawns Claude/Codex as real host processes via a bridge for full PTY support.
Use cases
- Write code to resolve a Jira bug directly from the ticket
- Generate documentation from a Notion ticket using Claude
- Review and annotate ticket history with a shared Markdown view
- Estimate LLM token costs before committing changes
- Run the tool in Docker for reproducible local environments
Ticket Terminal vs alternatives
 Ticket Terminal |  Cursor |  OpenAI Codex |  Aider |  Gemini CLI | |
|---|---|---|---|---|---|
| Best for | Local AI sessions for ticket workflows | AI-assisted code editing | General terminal coding with Codex | Terminal pair programming | Google-based terminal AI |
| Pricing | Open source | Subscription | Subscription | Free | Free |
| DevHunt upvotes | 1 | 0 | 0 | 0 | 0 |
| Launched | Oct 2026 | — | — | — | — |
- Ticket Terminal vs Cursor: Cursor is an AI-enhanced code editor, while Ticket Terminal focuses on turning tickets into AI sessions.
- Ticket Terminal vs OpenAI Codex: OpenAI Codex provides a coding agent but lacks built-in ticket integration and local cost tracking.
- Ticket Terminal vs Aider: Aider offers AI pair-programming in the terminal but does not map tickets to sessions.
- Ticket Terminal vs Gemini CLI: Gemini CLI is a Google AI agent for the terminal without ticket-to-session features.
Ticket Terminal FAQ
What do I need to run Ticket Terminal?+
You need an authenticated Claude or Codex CLI and credentials for the Jira/Notion tracker you want to use.
Is Ticket Terminal multi-user?+
The public preview is single-user only.
Does it provide a security sandbox?+
No, it is not a sandbox; it runs the LLM agents locally on your machine.
Can I run it without installing Python?+
Yes, a Docker image is provided that includes all dependencies.
Is the project free to use?+
Yes, it is released under the Apache-2.0 license.
Summarized by DevHunt from github.com · Oct 12, 2026. Details may change; check the official site.
