Orynx

Hand your agent the ticket. Keep your flow.

Orynx is a developer-first, plug-and-play app on your laptop. Connectors bring the tickets, reviews and messages that need you into one inbox, and the coding agent you plug in, Claude or Codex today, builds a ticket in its own git worktree. You choose how far it goes: ask before every command, or push the branch and open the pull request on its own.

What it does

One inbox: know what needs you, and why

Orynx reads your assigned tickets, review requests, your own pull requests and the messages that name you, then shows only what is waiting on you. Each row says why it is there and how long it has waited, so the next step is obvious.

• Approve command: an agent session is waiting for your click before it runs a command.
• Review requested: pull requests that asked for your review, longest wait first.
• Checks failing: your own pull requests with red checks or unresolved comments.
• Due tomorrow: assigned tickets by due date, with high-priority bugs on top.
• No reply: Slack and Discord messages that named you and still wait on your reply.

Your sprint, with your agent on the board

Board or list, filtered by assignee, status, type, priority and due date. Every card shows where its agent session stands, and any card can start one.

Delegate the work, stay close to the change

A session takes a ticket from brief to pull request in five visible steps: plan, build, test, review and pull request. Step in at any of them, or let it run.

1. Start from a ticket or a sentence. Paste a Jira key, pick a ticket from the board, or describe the task. Add pull requests, files and Slack or Discord threads as context, then choose the repository, the agent and the model.
2. The agent works in its own worktree. Each session gets a fresh git worktree and branch, so your main checkout stays untouched. Watch the plan, the files the agent reads and every edit as it happens.
3. Your settings decide what runs. The agent does what you allowed in Settings and asks for the rest: allow once, always allow, or deny. Review the diff file by file and ask for changes without starting over.
4. Ship your way. The agent drafts the pull request title and description. Push and open it with one click, or allow it to push the branch and open the pull request on its own.

Your rules: as hands-on or hands-off as you like

Pick a level in Settings › Coding agent, then set any kind of call to Allow, Ask or Block. The agent checks your settings before every call.

• Three levels to start from. Cautious asks before every edit and command. Balanced edits freely and runs your allowed commands. Hands-off runs, pushes and opens pull requests by itself.
• Your own mix. Edits, commands, the network, deleting outside the session's copy, pushing and pull requests each have their own row.
• Pull requests without the click. Allow push and pull request, and the agent ships the session's branch as you, never forced. Until then, it never pushes on its own.
• Sandboxed unless you say so. Commands run with no network and write only to the session's copy. Each risky row warns you when you allow it.
• Stop at any moment. Stop the agent mid-step, or discard the session and its worktree.

Local-first: your workspace, on your machine

There is no Orynx cloud. Orynx is a small server and a web app, both on your laptop.

• Tokens in your OS keychain. Jira, GitHub, Slack and Discord tokens are saved in your keychain and never reach the browser.
• Bound to 127.0.0.1. The server listens only on this computer and checks a token on every request. Your other devices reach it at https://orynx.local through a front door that asks for the password you choose when you set up Orynx (see Install).
• A local cache. Synced tickets and pull requests live in one file on your disk.
• Only what you connect. Orynx talks only to the connectors and agent you plug in: Jira, GitHub, Slack and Discord, and Claude or Codex, today.

This is the beginning of the README. Read the rest at the original. Read the full README ↗