Odin is one system for building software with clients. Stakeholders review real screens, plans cite what they decided, sprints run on the same projects, and a bug reported on the live site comes back as a pull request.
Harbor & Pine, an outdoor retailer, wants customers to start returns online. Here is that project in Odin, from the first conversation to the fix for its first bug.
Harbor & Pine is a sample client. The screens are drawn from Odin's own.
Start with a conversation in the AI Workspace, or write it yourself. The brief has eleven fields, from objective to success metrics, and every later step points back to it.
It drafts up to twelve requirements questions at a time, each tied to the brief line it came from. Stakeholders answer through a private link, with no account to create, or by replying to the email.
A coding agent builds a review package of screenshots and clickable prototypes. Reviewers step through it, mark up each screen and give it a verdict. Progress saves as they go.
Odin summarizes where reviewers agree and where they differ. People with decision rights record the outcome, and each decision lists the verdicts and comments behind it.
Odin drafts a plan whose acceptance criteria name the decisions they come from, then proposes stories for anything not yet covered. Approved work goes into sprints and onto the board.
One script tag adds Bug Reporter to any site. A report carries the screenshot with the tester's markup, the console and the pages they visited, and it becomes an Odin ticket with the same ID.
It works in an isolated Git worktree, runs the tests a change of that size needs, and opens a pull request with the evidence. A person merges it, and the reporter gets an email that explains the fix in plain words.
Ava answered the first question, reviewed the screens and reported the bug. The email about the fix came from the same project, and her next idea starts a new brief.
No mock-ups in this part. These are Odin's own screens with sample data, in whichever theme you're using now.
Home ranks what to do first and says why. Here a sprint is behind, and Home offers ways back on track.
In the old stories, Odin kept two ravens, Thought and Memory. Every day they flew over the world and came back with what they had seen. Odin's assistant has the same two jobs.
Ask the AI Workspace a question and it answers. If changes would help, it says what it would change and waits for your go-ahead. Tell it to do something and it does it in Odin, as you, with your permissions. It has 128 tools for plans, sprints, tickets, schedules, time, files, requirements and its own memory.
Sprint 15 is slipping. Move what you need to, and let Priya know.
Used 4 tools
Sprint 15 is past halfway with 47% of points done. I moved "Store drop-off without a label" (8 pts) to Sprint 16 and gave "Refund status emails" to Sam, who has 6 free hours; Priya was 4 hours over. My comment for Priya mentions her, so Odin will email her.
Add a comment
The comment waits for you to confirm. The other two changes are already made.
Odin keeps a short summary of every project, epic and story, and a memory of decisions, risks, outcomes and facts that it searches by meaning or keyword. People can add, correct and forget entries.
D-07: the return reason is optional.
Round 2 verdicts, topic "Return reasons"
Customers look orders up by email or phone. The order number is optional.
Topic answered Oct 2
Carrier API sandbox is down until Oct 20.
Raised by Marcus Chen
Harbor & Pine support is open 8 to 6 Pacific, Monday to Saturday.
Brief, current state
Sprint 14 closed 3 points short. CSV export moved to Sprint 15.
Sprint 14 review
Refunds go back to the original payment method.
Brief, proposed solution 4
Nothing in memory matches that.
Odin's MCP server gives ChatGPT, Codex, Claude and other MCP clients 121 tools, 48 that read and 73 that write. They cover projects and the full brief, epics, stories and tasks, the board, sprints, tickets, files, time and staffing, risks and milestones, workflows, comments, requirements feedback and review package uploads.
Bug Reporter adds a bug button to any website with one script tag. This page has one. Mark up what you see and follow the report to the fix. It's a demo, so nothing leaves your browser.
What a report from you would carry right now
Page trail 0
Console 0
This is your real visit to this page. A report would also carry the screenshot, your markup and any files you attach.
Draw on the page to show what's wrong.
The loop runs on a full delivery platform, so portfolio, people and money live with the work instead of in another tool.
Odin keeps an append-only audit trail and writes hash-chained exports to S3 under Object Lock. Each day's export includes the fingerprint of the one before, so editing any entry breaks every link after it. Try it: change an entry below.
All five exports verify.
Tell us what you build and who you build it with. Someone on the team reads every request.
