The workspace youragents work in.
Your board, your wiki and your people in one place. Hand Claude Code, Cursor or Codex a ticket reference, and the session reports back there: which tool, which teammate, how many tokens, still running or done.
Rebuild the landing page around the live agent board
Invite expiry copy
Whiteboard export
Tag people in ticket comments and email them
Address tickets by reference in URLs
A ticket reference is the whole handoff. Whatever your agents do comes back where the team already looks.
One workspace, not three tabs
The board, the wiki and the whiteboard are the same place. A ticket links a page, a page points back at the ticket, and nothing is kept in sync by hand.
Works with what you already run
Claude Code, Cursor, Copilot, opencode. The CLI writes the ticket into the rules file your agent already reads, so there is no plugin to install and nothing to migrate.
Give an agent a ticket, and the team watches it happen
Agents already write a large share of your code. They just do it in someone's terminal, where the rest of the team can't see it. This is the part we actually built Source for.
- 01
Copy the ticket reference
Every ticket on a board has one, like NS-47. That reference is the whole handoff: no export, no summary to paste, nothing to keep in sync.
- 02
Run one command where you code
npx neuvikon start writes the ticket into your agent's own rules file. Claude Code, Cursor, Copilot, opencode. No plugin, and no lock-in to one vendor.
- 03
The board shows the session
The ticket picks up a live ring: which tool is working, which teammate started it, and when it last checked in. Nobody has to ask for a status.
- 04
Tokens land on the ticket
When the session ends, its own token count is attributed to that ticket, that person and that project, not dumped into one org-wide total at the end of the month.
Rebuild the landing page around the live agent board
An agent is only as good as what it can read
Pages link to each other with [[brackets]], nest into one another, and the graph shows what that adds up to. It's where the decisions live, so the context a session needs is already next to the work, not in someone's head.
Read this session
- Landing page brief
- Design tokensnested
- Voice & tonenested
- Board spec
- Ticket referencesnested
- Agent sessionsnested
- Team handbook
- Billing notes
Drag a node. The graph settles with the same physics it does in the app.
An organization with a real shape
Invite your people, group them into teams and projects, and set who reports to whom. The chart is computed from those reporting lines every time you open it. It isn't a diagram somebody drew once and stopped updating.
- Owners and members
- Two roles, and an organization can have several owners. Nobody needs an admin tier to get their work done.
- Teams as colour, not levels
- Someone can report to the CTO and still sit in Design, so team membership is drawn on the person, never as a box above them.
- Job titles from a list
- Positions are a set the organization curates, so the chart stays readable instead of collecting five spellings of the same role.
Agent spend you can point at
Org-scoped API tokens keep every session attributable, so a finished run lands on a ticket, a person and a project. At the end of the month you get a breakdown you can read, not one number to argue about.
- Per project
- See which board is consuming the budget before the invoice tells you.
- Per member
- Sessions are attributed to the teammate whose token started them.
- Input vs output
- The split that actually drives the bill, broken out rather than summed.
Two hours nobody had to watch
One session on NS-47, beat by beat. It picks the ticket up, reads the wiki, asks the team a question and hands the ticket back in review with the cost already on it.
00:00
Handed over
One command names the ticket. The reference is written into the rules file the agent already reads. No plugin, nothing to migrate.
$ npx neuvikon start --ticket NS-47
00:02
Picked up
NS-47 moves to In progress on its own, and the card starts saying who is on it.
Claude Code · started by Ogulcan
00:09
Reading the wiki
The brief links Design tokens and Voice & tone, so the constraints arrive before the first line of code does.
3 pages read
01:04
Asking the team
A comment on the ticket tags Deniz and emails him the thread. The question and the answer stay on the ticket.
@deniz · mailed
01:47
Cost, attributed
Tokens land on the ticket that spent them, then roll up per project and per person. No one has to guess what a feature cost.
128k in · 34k out
02:05
Handed back
The session closes and NS-47 sits in review with everything it took to get there still attached to it.
$ npx neuvikon stop
- elapsed
- 02:05 elapsed
- tokens
- 162k tokens
- pages read
- 3 pages read
- question
- 1 question
It starts as a workspace for one person
No organization to create, no seats to buy. Your own pages, whiteboard, todos and habits are free and stay free. The team side is there for the day you want it.
Pages
Write, link pages with [[brackets]] and reference a ticket with #. This one is the real editor, so type in it.
Todos
A list per day, so the small things don't get lost inside a page. Go on, tick one off.
Whiteboard
An open canvas for the sketches and plans a document can't hold. This one is the real thing, drawn in Excalidraw.
Habits
Mark the things you do every day and watch the streak build. These squares are clickable too.