arachne
linked project context

Link sessions. Share project patterns.

Arachne lets you create sessions inside a project, link them on a canvas, and ask the current agent to follow patterns from a peer session. Tool calls can receive a `peer_session_id` and read the linked project for exact context. Built with Rust.

nested sessions
linked canvas
peer reads
linked session canvasproject: backend rewrite
current app
new project session
openapi ref
schema layout, client pattern, errors
rust service
handlers, commands, event streams
admin ui
forms, tables, route conventions
current prompt

can you follow the same OpenAPI pattern from the linked session?

projects contain sessions
sessions link on canvas
peer_session_id tools
openai and anthropic
Why Arachne?

Ask one session to follow another session's project pattern.

Create a session for the current work, connect it to sessions that know reference projects, then prompt normally. The agent can call tools against linked peers instead of relying on a hand-written summary.

1. create a project and nest sessions inside it

2. link sessions together on the canvas

3. ask: can you follow the same OpenAPI pattern?

4. tools read linked peers through peer_session_id

session flow

Build context by connecting sessions, not by rewriting prompts.

01 / project1/6

Sessions nest inside a project.

A project is the container. Inside it, you create sessions for the current build, references, experiments, or prior codebases you want available.

01 / project

Sessions nest inside a project.

project/backend-rewrite -> sessions[current, openapi-ref, admin-ui]
02 / canvas2/6

The canvas decides who can share context.

Drag sessions into a web and link them. Those dotted edges become the visible boundary for which peers can be queried.

02 / canvas

The canvas decides who can share context.

link current -> openapi-ref -> rust-service
03 / tools3/6

Tool calls can target linked peers.

When the current agent needs a pattern, its read/glob/grep/plan tools can receive a peer_session_id and inspect the linked project directly.

03 / tools

Tool calls can target linked peers.

grep(pattern='OpenAPIClient', peer_session_id='openapi-ref')
04 / plan4/6

Plan mode keeps exploration read-only.

Use plan mode when you want the agent to study linked sessions, compare patterns, and propose changes without mutating files.

04 / plan

Plan mode keeps exploration read-only.

mode=plan -> inspect linked projects, no writes
05 / build5/6

Build mode lets the agent implement.

When the plan is right, switch to build mode. The agent can edit the current project while still reading peers for pattern fidelity.

05 / build

Build mode lets the agent implement.

mode=build -> apply OpenAPI pattern in current session
06 / providers6/6

Bring the provider you already use.

Arachne supports OpenAI, Anthropic, OpenAI-compatible providers, and custom endpoints across the same linked-session workflow.

06 / providers

Bring the provider you already use.

provider=openai | anthropic | openai-compatible | custom
built with rust

Built with Rust for durable projects and extensible agent behavior.

Arachne persists projects and sessions so the canvas can become a long-running map of how work evolves. The agent crate is modular by design, making new tools, providers, and behaviors easier to add.

persistence
Projects, sessions, messages, and canvas state are kept around instead of disappearing after one run.
agent crate
The modular `arachne-agents` crate keeps LLM, tool, session, and event logic isolated enough to extend.
contributions
New providers, tools, session behaviors, and UI ideas are welcome as the project grows.

Prompt the current session. Let linked sessions supply the pattern.

"Can you follow the same OpenAPI pattern?" becomes actionable because the agent can inspect the linked session's project instead of guessing from memory.