Your AI creative teammate

A one-shot generator can hand you a file. Shyne is built around a different idea: the agent is a teammate on the same live canvas you are looking at. You do not wait for a ZIP. You do not paste the result into another editor to make it real. The work appears as frames, sequences, and nodes you can select, undo, and keep.

That sounds like a slogan until you watch it happen. Someone asks for a nine-slide investor update. The first title lands. A chart frame appears. A colleague, already in the project, moves a logo while the teammate is still writing the appendix. Nothing remounts. The undo stack is still the undo stack. That is the product we mean by teammate.

What that means in practice

You open a project, ask for a deck, a post, a one-pager, or a short film, and the work appears as real frames and nodes. You can stop it, move a heading, change a color, or ask for another pass without starting over.

The agent does not keep a private copy of the document. It uses the same operations the rest of Shyne uses, so every edit lands in the shared project and shows up for anyone who has it open. The public names look like the rest of the system: canvases_read, frames_apply, nodes_apply, sequences_create. Those are not implementation trivia. They are the reason the teammate cannot “rewrite the file” in a way the editor cannot see.

A useful first prompt is specific. “Create a six-slide launch presentation for a design-conscious founder audience. Use our current theme, concise copy, and a different composition on each slide.” Vague prompts produce vague frames. Specific prompts produce a sequence you can argue with.

When the first pass is wrong, select the frame that is wrong. The current selection rides with the next prompt as context. You do not have to paste a screenshot into the chat and hope the model remembers which heading you meant. You point at the work.

A peer, not a rewriter

A Shyne project is one document in a Durable Object. Humans connect over the editor websocket. The agent becomes another caller of the same registry, for whichever project a call names. Two consequences follow.

Concurrency is free in the ordinary CRDT sense. A human dragging a frame while the agent recolors a heading are two writers on different keys. Both edits persist. Collaborators each bring their own seat — their own agent, their own identity. The document serializes the writes. It does not make you take turns.

There is no whole-document rewrite lane. The agent orients with a structured read, edits structured nodes, and verifies with a preview or another read. HTML is accepted only at an explicit import or create boundary, then discarded after the node graph is written. If you have used tools that regenerate the entire page on every prompt, you already know why this matters. A rewrite lane is how your last correction disappears.

Always on brand

A teammate is only useful if it remembers how you look. Brand colors, type, and the files you have already approved stay with the project. The next draft starts from that, instead of inventing a new look each time.

Every project carries a theme: shared colors, type, and spacing that keep new work related. Change the theme once and work built on it can follow. The file library holds uploads and generated media so the teammate is not fetching a logo from a half-remembered URL. If you already have a PDF, a previous deck, or a mark, attach it. Small images and PDFs can ride with the first prompt. Larger files land in the project so later turns can use them.

On-brand is not a filter at the end. It is the default of a project that already has a personality. If the teammate misses, you correct the node. The correction is the new source of truth. You should not have to maintain a slide master in one tool and a social template in another.

What the teammate can do

It can list the projects you can reach, read canvases, apply frames and nodes, build and reorder sequences, move work between canvases when that is allowed, export, and work with files you attach. When publishing is enabled, it can preview a post or ask to post or schedule it to a connected channel. It can save brand and memory entries you have asked it to keep.

It can work on video as a timed sequence: read the timeline, add and move clips, split or retime them, and inspect exact moments. That is the same document, not a side editor.

It can use the web when a turn needs a public page, and it can run ordinary file tools in its own workspace. The documents never live in that workspace. Canvas writes still only flow through the document operations. That split is how we keep a bash tool from becoming a second, invisible editor.

What the teammate cannot do

It cannot silently become the owner of the account. Restore, permanent project deletion, and credential management stay human. Provider tokens are never returned to the agent. Publishing and connector writes are consequential actions: the agent can request them, but Shyne shows you what will happen and asks permission before the call runs.

It cannot invent a canvas target when the project has several canvases and none was named. Reads never create a canvas. Mutations never fall back to a magic main document. If the agent says no project or canvas was specified, the next instruction is to list them and name the exact ids. That is not ceremony. It is how we keep an edit from landing in the wrong infinite space.

It cannot see every linked project in a global list. Link-only access does not widen listing. You open or address that project so access can be rechecked directly.

Two homes, one seat

There is one agent runtime and two homes. On the web, the agent runs in a per-user cloud sandbox. In the desktop app, it runs as a local child process. Both talk to the same AI gateway with a user credential. There is no service token and no provider key sitting in the product for the teammate to borrow.

Every model call is a user-authorized call. Text and media go through the factory. Spend lands in a ledger. That is not a billing essay; it is the reason “the teammate” is attached to a person, not to a shared robot that acts as the company.

Each person who joins a project brings their own seat. You do not share one agent the way you might share one design file login. You share the document. The hands stay yours.

Bring your own agent

The in-product teammate is the default. It is not the only way in. Shyne speaks MCP from the desktop app at http://127.0.0.1:7655/mcp and from the hosted product at https://mcp.shyne.ai/mcp. Claude Code, Cursor, Claude Desktop, VS Code Copilot, and other MCP clients can edit the same canvas. You watch the work appear as live presence.

Desktop MCP is loopback-only and acts as the signed-in user. Anything on your machine that can reach the port can act through that session. Close the app to stop the endpoint. Hosted MCP uses OAuth and the same project ACL the editor uses.

If you already live in an agent, you do not have to move your whole practice into our composer. You connect, name a project, and work. The document does not care which client held the pen.

Not a generator, a coworker

Generation is useful. It is not the product. The product is staying in the work: watching the teammate, redirecting it, and shipping from the same canvas you edited together.

A generator that hands you a file has a clean demo. The demo ends when you open the file. A teammate has a messier demo and a better Tuesday. You keep the sequence. You keep the brand. You keep the comments you have not resolved. You export PNG, PDF, HTML, PowerPoint, or MP4 when you need a file. You post or schedule to a connected channel when you are ready, with Shyne’s permission gate in front of agent-initiated sends.

If you have been bouncing between a chatbot, a slide tool, and a video editor, the teammate is the attempt to put those hours back on one canvas. It will still be wrong sometimes. When it is wrong, you are still in the document.

How to try it this week

Create a project. Attach the two or three files that already define the look. Ask for one finished artifact — a six-slide launch deck, a three-post carousel, a thirty-second sequence — with an audience and a length. Watch the first pass. Correct the worst frame by hand. Ask for a second pass on that frame only. Export it, or post it to a connected channel when it is ready.

That is a complete session. You do not need a tour of every tool. You need one piece of work that is still yours after the teammate has been through it.

The longer you stay on the canvas, the more obvious the difference becomes. Other tools generate. Shyne stays.