retrieve
Pull the thread.
Find the memory, decision or work item that gives the next move its meaning. Allye turns scattered context into a trail you and your agents can follow.
work items · memories · docs
- ALLYE CONTEXT
- Plugin workflow
- Release checklist
- Context before action
- OAuth-only MCP connection
- Keep authentication on the same domain
- Alpha release principle
- Memory supports review
- Team working agreement
[ INCOMING TRANSMISSION // CONTEXT OS ]
AI forgets. Allye remembers.
Allye is the context OS for teams shipping with AI — one live workspace for work, memory, docs and rules, beamed straight into the agents you already use. Less re-briefing. More shipping.
FREE DURING ALPHA · REMOTE MCP / URL + OAUTH · PI & OPENCODE READY · CLAUDE CODE & CODEX TESTED
[ SIGNAL DEGRADED ]
Context gets lost
between sessions.
- Every new session starts from zero — the agent never saw yesterday's decision.
- Work lives in one tab, docs in another, memories nowhere.
- Skills and rules get re-explained instead of reused.
- Review happens without the reasoning that produced the work.
WORK ITEM 4821DECISION.LOGMEMORY: AUTHSKILL: REVIEWDOC: SETUPTHREAD #067
ALLYE / ONE_WORKSPACESYNC
WORKMEMORYDOCSSKILLS
FIG.02 — SCATTERED SIGNALS, ONE WORKSPACE
[ MEMORY ATLAS ]
Your work has
a memory.
Every useful answer sits inside a larger story. The atlas makes that story legible — then makes it available wherever you build.
ATLAS IS LISTENING 01/04
understand
See the shape.
Related ideas become a living map. Trace why a decision happened, what it touches and which context is safe to carry forward.
semantic links · sectors · scope
act
Move with context.
Bring the right slice of your workspace into the agent you already use. Less re-briefing, more focused work that compounds.
remote MCP · OAuth · plugins
preserve
Leave a trail.
Save the decision while it is still warm. Your future self — and your future agents — inherit the reasoning, not just the output.
skills · rules · continuity
[ THE DESK ]
A desk, not
a pile of tabs.
Every screen has a job. A set of surfaces that make the work legible — for you and for the agents beside you.
ALLYE_DESK / DASHBOARD.SYSLIVE
SAMPLE WORKSPACE
CONTEXT SYNCONLINE
MEMORY GRAPHACTIVE
REVIEW GATEHUMAN
ACTIVITY STREAM
memory saved — decision: remote MCP only
review approved — story: atlas rail polish
skill mounted — review checklist
work item moved to code review
doc updated — context os overview
SIGNAL FLOWCONTEXT MOVING THROUGH THE WORKSPACE
01 / MISSION VIEW
Know what is moving now.
A calm read on the workspace: what is in flight, what is blocked and where attention belongs — without babysitting another dashboard.
SURFACE 01/05SAMPLE TRANSMISSION
[ MCP BRIDGE ]
One remote connection.
Every agent you run.
A remote MCP server reached with a URL and an OAuth consent — nothing else. No local database, no tokens in prompts, no context copies.
AGENT HOSTyour client
ALLYE CONTEXTwork · memory · docs · skills
THE WORKshipped with context
REMOTE-CONNECTION.MCPOAUTH
$ connect allye --remote
endpoint<MCP_URL_PROVIDED_BY_HOST>ready
authOAuth 2.0 / browser consentverified
scopework · memory · docs · skillsscoped
context bridge established session managed by your host
PI / OPENCODEcustomizable harness, more autonomy
RECOMMENDEDCLAUDE CODE / CODEXmay need explicit asks for memory/skills
HIGHLY TESTEDCURSOR / OTHER MCP CLIENTSsame remote connection
COMPATIBLERemote URL + OAuth only. No stdio, no PAT, no REST endpoints to babysit.
[ PLUGIN / HARNESS ]
A harness
with opinions.
The Allye plugin teaches your host how the workspace thinks: memory-first habits, skills, handovers and review gates — installed once, carried into every session.
- PI / OPENCODE — recommended. The most customizable harness and the most autonomous plugin workflow.
- CLAUDE CODE / CODEX — highly tested over the same remote connection.
- CURSOR / OTHERS — compatible MCP clients plug into the same context.
Heads up: Claude Code may need explicit requests to pull from Allye Memory or to use specific skills — the Pi / OpenCode flows handle that more proactively.
PLUGIN / SKILLS.SYSLOADED
[ ACCESS LEVELS ]
Enter the alpha.
Keep the signal.
Allye is in alpha. Get full access while we build the Context OS with the teams using it.
ALPHA / SOLOAVAILABLE
$0 / during alpha
Free, full access to the available workspace while we are in alpha.
- ✓ Work items, boards and sprints
- ✓ Semantic memory graph
- ✓ Docs, skills and rules
- ✓ Remote MCP via URL + OAuth
NO CREDIT CARD REQUIRED
TEAMS & ENTERPRISECOMING SOON
/ in the works
For organizations that need control over how context is shared.
- ◌ Shared docs and skills
- ◌ Team management
- ◌ Permissions and governance
- ◌ Workspace controls
JOIN THE ALPHA TO GET THERE FIRST
[ FREQUENTLY DECODED ]
Questions from
the static.
During the alpha, yes. You get full access to the available workspace — work items, memory, docs, skills and the remote MCP connection — with no credit card. Teams & Enterprise plans arrive later.
Through a remote MCP server only: a URL plus an OAuth consent flow managed by your host. No tokens pasted into prompts, no local database, no context copies floating around.
Pi and OpenCode are recommended — they allow a more customizable harness and more autonomous plugin workflows. Claude Code and Codex are highly tested, and Cursor plus other MCP-compatible clients can connect too.
It can, but it may need explicit requests to pull from Allye Memory or to use specific skills. The Pi and OpenCode plugin flows handle this more proactively by design.
It compounds. Decisions, memories, docs and skills persist in the workspace and are available to every connected session — and shipping still passes through human review.
Coming soon: shared docs and skills, team management, permissions and governance. Joining the alpha is the fastest way to get there early.
[ END OF TRANSMISSION — FOR NOW ]