Jeddy is your one assistant for work. It carries your context, uses its skills and sub-agents to do the job within explicit capabilities, approval rules, budgets, and placement, and brings you the decisions only you can make. Same Jeddy in the cloud or on your machine.
Start with what you want finished, not a prompt you have to keep steering. A job has a title, an optional definition of done, and a priority. It can come from you, from your manager, or from a trigger.
Today separates what is ready from work already in progress and work waiting on you. You keep priority; your Jeddy keeps the state visible.
Hand a job to your Jeddy and it picks the right sub-agent for it. The run is admitted against that sub-agent's published identity, skills, connectors, policy, and placement.
The workroom keeps the job, your notes, status, and result together. When policy requires a human decision, the work waits visibly and the approval lands in Inbox.
Finished work moves to Done with its summary and the sub-agent that did it. Open the workroom to inspect the runtime evidence attached to a completed run, then record whether the result was useful.
You never manage a bench. Your Jeddy knows how to do things (skills), repeats the jobs you give it often (apps), and dispatches bounded workers when a job calls for one (sub-agents). Each sub-agent has a published identity, immutable revisions, and an approval posture of its own.
Versioned, reusable, with the connectors, approvals, and forbidden actions they need.
A job packaged with its skills, connections, and approval posture, run on demand or on a trigger.
Bounded workers your Jeddy picks for a job, each with a placement you chose.
A leader assigns jobs to people, not to their Jeddys. The person's Jeddy does the work and the person signs off. The team shares skills, sub-agents, model policy, budgets, and evidence, and the leader sees outcomes rather than private context.
Your Jeddy owns your work record. Its sub-agents execute in their chosen runtime. Connected apps remain authoritative for their projects, messages, documents, and transactions.
Priority, Today, workroom context, Inbox decisions, results, and usefulness.
Attempts, checkpoints, tool calls, usage, and evidence for the selected lane.
The source application remains authoritative for every accepted business change.
Start with Solo. Bring your own provider when you need it.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect